What if we would degrade LO tasks in mixed-criticality systems?

نویسنده

  • Marcus Völp
چکیده

Mixed-criticality (MC) systems [1] allow tasks of different importance (or criticality) to be consolidated into a single system. Consolidation facilitates resource sharing (even across criticality levels) and hence bears the potential to reduce the overall amount of resources needed. However, there is a common misconception that recurs in literature about Vestal’s model: the false believe that low criticality tasks are degraded to soft real-time or even best effort tasks. In this work, we not only wish to clarify this misconception but also ask ourselves what would happen if we degrade LO tasks. Revisiting Quality Assuring Scheduling (QAS) [2], [3], our goals are stochastic guarantees for LO completion in addition to and replacing the hard MC guarantees if LO tasks are soft real-time. In this WIP report, we focus on properties of dropped LO tasks (while keeping hard MC guarantees) such as: “What is the likelihood of lower criticality jobs being dropped because higher criticality jobs exceed their low WCET estimates?”, “What is the likelihood of dropped jobs to still make their deadline?”, and “What is the expected time / Q-percentile for dropped jobs to catch up with their execution?”. Part of our future work will be to extend these guarantees and to develop MC schedulers for a combination of hard and soft real-time tasks. Notice though, that the assumptions in this report still limit the applicability of our results. We indicate how we plan to relax them in the future. Most notably, we assume that jobs arrive in their synchronous arrival sequence and that executiontime distributions are known. The latter we plan to replace with confidence of WCET estimates.

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

منابع مشابه

Incorporating The Notion of Importance into Mixed Criticality Systems

Mixed criticality systems offer the opportunity to integrate system components with different levels of assurance that previously may have been placed on different nodes. While the vast majority of mixed criticality work features a HI and a LO criticality level, LO criticality tasks should not be mistaken for tasks with little value. Such tasks might contain mission critical functionality and a...

متن کامل

Tightening Critical Section Bounds in Mixed-Criticality Systems through Preemptible Hardware Transactional Memory

Ideally, mixed criticality systems should allow architects to consolidate separately certified tasks with differing safety requirements into a single system. Consolidated, they are able to share resources (even across criticality levels) and reduce the system’s size, weight and power demand. To achieve this, higher criticality tasks are also subjected to the analysis methods suitable for lower ...

متن کامل

Mixed Criticality Systems: Beyond Transient Faults

Adopting mixed-criticality architectures enable safe sharing of computational resources between tasks of different criticalities consequently leading to reduced Size, Weight and Power (SWaP) requirements. A majority of the research in mixed-criticality systems focuses on scheduling tasks whose Worst Case Execution Times (WCETs) are certified to varying levels of assurances. If any given task ov...

متن کامل

MCFlow: Middleware for Mixed-Criticality Distributed Real-Time Systems

OF THE DISSERTATION MCFlow: Middleware for Mixed-Criticality Distributed Real-Time Systems by Huang-Ming Huang Doctor of Philosophy in Computer Science Washington University in St. Louis, 2012 Research Advisor: Professor Christopher D. Gill Traditional fixed-priority scheduling analysis for periodic/sporadic task sets is based on the assumption that all tasks are equally critical to the correct...

متن کامل

An Extended Fixed Priority Scheme for Mixed Criticality Systems

This paper considers a novel implementation scheme for fixed priority (FP) uniprocessor scheduling of mixed criticality systems. The scheme requires that jobs have their execution times monitored. If system behavior inconsistent with lower criticality levels is detected during run-time via such monitoring, (i) tasks of lower criticalities are discarded (this is already done by current FP mixed-...

متن کامل

ذخیره در منابع من


  با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

عنوان ژورنال:

دوره   شماره 

صفحات  -

تاریخ انتشار 2014